create vlan

create vlan [ vlan_name {tag tag} | vlan_list ] {description vlan-description } {vr name }

Description

Creates a named VLAN.

Syntax Description


`vlan_name`	Specifies a VLAN name (up to 32 characters).
`vlan_list`	Specifies a VLAN list of IDs.
tag	Specifies a value to use as an 802.1Q tag. The valid range is from 2 to 4095.
`vlan-description`	Specifies a VLAN description (up to 64 characters) that appears in show vlan commands and can be read from the ifAlias MIB object for the VLAN.
`name`	Specifies a VR or virtual routing and forwarding (VRF) instance in which to create the VLAN. Note: User-created VRs are supported only on the platforms listed for this feature in the Switch Engine v33.1.1 Licensing Guide document. On switches that do not support user-created VRs, all VLANs are created in VR-Default and cannot be moved.

Default

A VLAN named Default exists on all new or initialized Extreme switches:

It initially contains all ports on a new or initialized switch, except for the management port(s), if there are any.
It has an 802.1Q tag of 1.
The default VLAN is untagged on all ports.
It uses protocol filter any.

A VLAN named Mgmt exists on switches that have management ports:

It initially contains the management port(s) the switch.
It is assigned the next available internal VLANid as an 802.1Q tag.

If you do not specify the VR, the VLAN is created in the current VR.

If the VLAN description contains one or more space characters, you must enclose the complete name in double quotation marks.

Usage Guidelines

A newly-created VLAN has no member ports, is untagged, and uses protocol filter any until you configure it otherwise. Use the various configure vlan commands to configure the VLAN to your needs.

Internal VLANids are assigned automatically using the next available VLANid starting from the high end (4094) of the range.

The VLAN name can include up to 32 characters. VLAN names must begin with an alphabetical letter, and only alphanumeric, underscore ( _ ), and hyphen (-) characters are allowed in the remainder of the name. VLAN names cannot match reserved keywords. For more information on VLAN name requirements and a list of reserved keywords, see Object Names in the Switch Engine v33.1.1 User Guide .

Note

If you use the same name across categories (for example, STPD and EAPS names), we recommend that you specify the identifying keyword as well as the actual name. If you do not use the keyword, the system may return an error message.

VLAN names are locally significant. That is, VLAN names used on one switch are only meaningful to that switch. If another switch is connected to it, the VLAN names have no significance to the other switch.

You must use mutually exclusive names for:

VLANs
VMANs
Ipv6 tunnels
BVLANs
SVLANs
CVLANs

Note

The VLAN description is stored in the ifAlias MIB object.

If you do not specify a VR when you create a VLAN, the system creates that VLAN in the default VR (VR-Default). The management VLAN is always in the management VR (VR-Mgmt).

Once you create VRs, ExtremeXOS allows you to designate one of these as the domain in which all your subsequent configuration commands, including VLAN commands, are applied. If you create VRs, ensure that you are creating the VLANs in the desired virtual-router domain.

Note

User-created VRs are supported only on the platforms listed for this feature in the Switch Engine v33.1.1 Licensing Guide document.. On switches that do not support user-created VRs, all VLANs are created in VR-Default and cannot be moved.

Example

The following example creates a VLAN named accounting on the current VR:

create vlan accounting description "Accounting Dept"

History

This command was first available in ExtremeXOS 10.1.

The vr option was added in ExtremeXOS 11.0.

The vlan-description option was added in ExtremeXOS 12.4.4.

The vlan_list variable was added in ExtremeXOS 16.1.

Platform Availability

This command is available on all Universal switches supported in this document.